Issue & Reproduction Steps

When importing a screen via devlink we get a 500 error when a dependent screen is missing

Solution

• Ignore missing dependent screen instead of throwing an error

How to Test

• Have a screen with a missing nested screen
• Try to export a process that uses the main screen

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-27169

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.